A community content record defines the layout of a community's web page. Default community layouts are provided, but you can move the iParts on the page.
Administrators can always view the Communities list, but you will want to allow non-Administrator users to view the Communities once the display is to your liking.
If you want change the look and feel of a community page, you can do so in the following ways:
■ By editing the website's definition and selecting different master pages and themes.
■ By modifying the selected theme (which affects all websites that share it).
Community layouts
Three content records with different layouts for your community iParts are provided by default.
■ The Community layout provides one of each type of Community iPart in a TwoColumns50-50 layout.
■ The Community Description layout has two iParts - one is an "About" iPart that displays the Long Description from the community definition, the second is a Recent Activity iPart that displays recent posts and comments.
■ The Community Post Summary layout displays a Recent Activity iPart that displays recent posts and comments, an Announcements iPart in a SingleColumn layout, and a Community Roster iPart in a TwoColumns50-50 layout.
Content records and iParts
A content record is an iMIS definition object, stored in the Document System, that specifies all the information needed to render a web page. Instead of hand-coding the contents of a web page for your website, you define some basic properties and tags for the content record, choose a content layout, add various iParts to the iPart zones in the layout, and then define the properties for each iPart. After the content record has been published to an .aspx file on the website, it is available for viewing by web browsers as a complete web page.
An iPart is a web widget in the ASP.NET environment. As with any web widget, you choose from different types of iParts to insert in the various iPart zones in the content layout, then you configure each iPart to populate that instance of it with the desired content. You can easily rearrange the rendered page contents by dragging an iPart to a different location within the iPart zones. A standard set of system-defined iParts are available in iMIS, but staff or consultants who are experienced in ASP.NET development can also easily add new iParts for use when authoring content.
■ The standard iParts supplied in the Content gallery all have a corresponding content type, which tells iMIS how to create the corresponding iPart within the system, how to edit it, how to display it, how to publish it, and so on.
■ New complex iParts that you add to your iMIS environment are also listed in the iPart Gallery and must also have corresponding content types.
■ A special ASI-supplied ContentWebUserControl content type is used as a generic default content type for all simple iParts, or for ad-hoc web user controls that have been manually added to a content record.
To see the Communities iPart gallery, you need a COMMUNITIES license.